Summary

This PR adds comprehensive HTTP client configuration support (timeouts, SSL, redirects) for 12 Spring AI model providers. The implementation is based on each provider's underlying HTTP client, ensuring consistency with Spring Boot's configuration patterns while maintaining backward compatibility.

Scope of Changes

Modified Providers (12 total)

1. DeepSeek - Chat model
2. Anthropic - Chat model
3. Azure OpenAI - Chat, Embedding, Audio, Image (multi-modal)
4. ElevenLabs - Audio model
5. Google GenAI - Chat and Embedding models
6. MiniMax - Chat and Embedding models
7. Mistral AI - Chat, Embedding, Moderation, OCR models
8. OCI GenAI - Oracle Cloud Infrastructure GenAI
9. Ollama - Local model support
10. OpenAI - Complete suite (Chat, Embedding, Audio, Image, Moderation)
11. Stability AI - Image generation
12. ZhiPu AI - Chat, Embedding, Image models

Providers Not Modified

• Vertex AI - Uses Google Cloud SDK with SDK-managed HTTP client
• PostgresML Embedding - Database connection, no HTTP client
• Transformers - Local model inference, no HTTP calls
• Hugging Face - Being migrated to RestClient by another contributor (avoiding duplicate work)

Implementation Approach

Pattern 1: RestClient-based Providers (Recommended)

Applied to 10 providers using Spring RestClient with RestClientCustomizer for configuration injection.

Providers: DeepSeek, Anthropic, ElevenLabs, Google GenAI, MiniMax, Mistral AI, Ollama, OpenAI, Stability AI, ZhiPu AI

Key Components:

1. ConnectionProperties Extension

   • Added nested HttpClientConfig inner class
   • Supports connectTimeout, readTimeout, redirects, sslBundle
   • Provides toHttpClientSettings() method for Spring Boot standard conversion

2. RestClientCustomizer Implementation

   • Created dedicated XxxRestClientCustomizer classes
   • Uses ClientHttpRequestFactoryBuilder to build request factory
   • Non-invasive configuration application preserving user customizations

3. AutoConfiguration Integration

   • Registers RestClientCustomizer bean
   • Supports spring.ai.xxx.http-client.enabled toggle
   • Conditional configuration, enabled by default

Configuration Example:

spring:
  ai:
    deepseek:
      api-key: ${DEEPSEEK_API_KEY}
      http-client:
        enabled: true
        connect-timeout: 10s
        read-timeout: 60s
        redirects: follow
        ssl-bundle: my-ssl-bundle

Pattern 2: Azure SDK-based Providers

Applied to 2 providers using Azure/OCI SDKs with direct timeout configuration in ConnectionProperties.

Providers: Azure OpenAI, OCI GenAI

Key Components:

1. ConnectionProperties Extension

   • Added connectTimeout and readTimeout properties directly
   • Applied during API client construction

2. Client Builder Integration

   • Sets timeout parameters when creating Azure/OCI clients
   • Uses SDK-native timeout configuration methods

Configuration Example:

spring:
  ai:
    azure:
      openai:
        api-key: ${AZURE_OPENAI_API_KEY}
        endpoint: ${AZURE_OPENAI_ENDPOINT}
        connect-timeout: 10s
        read-timeout: 90s

Key Design Decisions

1. Backward Compatibility

   • All configuration properties are optional
   • Can be completely disabled via enabled property

2. Unified Configuration Structure

   • Follows Spring Boot's HttpClientSettings standard
   • Property naming consistent with Spring Boot conventions
   • SSL Bundle integration support

3. Non-invasive Implementation

   • Uses RestClientCustomizer instead of direct RestClient modification
   • Preserves any existing user customizations
   • Supports user override via conditional annotations

4. Comprehensive Test Coverage

   • Added configuration property tests for each provider
   • Validates default and custom values
   • Integration tests verify actual HTTP behavior

Code Statistics

• Total Files Modified: 59
• Lines Added: 1,785
• Lines Removed: 87
• New Tests: Configuration property tests and integration tests for all providers

Main File Types Changed

1. AutoConfiguration classes - Added RestClientCustomizer bean registration
2. ConnectionProperties classes - Added HttpClientConfig configuration class
3. RestClientCustomizer classes - New dedicated customizer implementations
4. Test classes - Added configuration property validation and integration tests

Commit History

Chronological commit log:

1. 265ab8a9 - feat: DeepSeek: support HTTP client timeout configuration
2. 7b889293 - perf(deepseek): Adjust the configuration timeout method
3. 29eb9516 - perf(anthropic): support HTTP client timeout configuration
4. 5cafbb22 - perf(azure-openai): support HTTP client timeout configuration
5. 2b0dc840 - perf(elevenLabs): support HTTP client timeout configuration
6. f2930947 - perf(google-genai): support HTTP client timeout configuration
7. 109c0994 - fix(google-genai): Fix specification errors
8. 182a2c43 - perf(miniMax): support HTTP client timeout configuration
9. 6f788b39 - fix(minmax): Configuration error adjustment
10. 8c7cb3c8 - perf(mistralAi): support HTTP client timeout configuration
11. ebd61d81 - perf(oci-genai): support HTTP client timeout configuration
12. 719c239c - perf(ollama): support HTTP client timeout configuration
13. 4b1b566b - perf(openai): Support HTTP client timeout configuration and nested way using HttpClientSettingsProperties
14. 1f0cdf8e - perf(stability-ai): Support HTTP client timeout configuration
15. 6a780cc9 - perf(zhipu-ai): Support HTTP client timeout configuration

Usage Examples

Basic Configuration

spring:
  ai:
    openai:
      api-key: ${OPENAI_API_KEY}
      http-client:
        connect-timeout: 15s
        read-timeout: 120s

Advanced Configuration (SSL + Redirects)

spring:
  ai:
    anthropic:
      api-key: ${ANTHROPIC_API_KEY}
      http-client:
        connect-timeout: 10s
        read-timeout: 90s
        redirects: follow
        ssl-bundle: custom-ssl

Disable Custom Configuration

spring:
  ai:
    deepseek:
      api-key: ${DEEPSEEK_API_KEY}
      http-client:
        enabled: false  # Use default RestClient configuration

Testing

All modified providers include:

1. Default Configuration Tests - Verify default timeout values
2. Custom Configuration Tests - Verify configuration properties are correctly applied
3. Disabled Configuration Tests - Verify behavior when enabled=false
4. Integration Tests - Verify timeout behavior in actual HTTP calls

Related Issue

Resolves #4934

Future Work

1. Apply same HTTP configuration pattern to Hugging Face provider once RestClient migration is complete
2. Consider adding similar support for future providers
3. Documentation updates: Add HTTP configuration examples for each provider

Notes

• This PR does not change any existing API behavior
• All configurations are optional with sensible defaults
• No impact on existing users who don't use these configurations
• Configuration properties follow Spring Boot naming conventions for ease of use